Just did the experiment and attached the logs to FB21378487. Hope it helps! [quote='871179022, Developer Tools Engineer, /thread/800067?answerId=871179022#871179022'] Add the following to your ~/.lldbinit: log enable gdb-remote packets --timestamp -f /tmp/log_packets.txt [/quote]

I tried to disable swift-tasks-plugin-enabled as you described, but that barely had noticeable effect (<1s difference). With the debugger attached (and iPhone connected with USB) our app becomes responsive after about 6-7 seconds from start, while this time decreases to less than 1s if I turn off "Debug executable" option in scheme. I collected lldb-rpc-server sample as you described and added it to FB21378487. Hope it would be helpful!

Just checked new Xcode 26.2 with iOS 26.2 and the debug builds startup time indeed improved significantly. We still have ~7 seconds of initial sluggishness (difference between debug executable on/off), but it's way better than it was before! 👍

One year later it's still there. Is an expected behavior after all?

Me too

Answer is here https://stackoverflow.com/a/79342378/2432781

The release notes of Xcode 13.3 beta 2 mentions "code completion" 12 (!) times. Unfortunately I cannot test it yet, since it requires macOS Monterey. Did anybody tried it?

Did you get any reply to your bug report?

Xcode 13.2 beta 2 (13C5081f) - same story. Back to Xcode 12.5.1 again 🙁

Still not fixed in Xcode 13.2 beta (13C5066c)

I occasionally have the same problem on my MacBook Pro 2019, 16Gb RAM. Most often it happens if I try to do a cold build for simulator (most of the time I use real devices). If I run top -o mem while it's happening I see literally tens of swift-frontend processing each taking ~200Mb. After about a minute or two RAM congestion wears out and it starts to behave normally. I wonder if anyone also see this?

Same here. Have info about 1-year old versions, but not later.